Set computed flag for 'max_pods_per_node' in google_container_node_pool #2077
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After upgrading
terraform-provider-google
to version 1.18 users will notice an unnecessary Terraform plan difference in existing node pool configurations. This is caused by a new configuration parametermax_pods_per_node
which was introduced in #2038. At the moment it expects end users to explicitly define the parameter value in the configuration or it expects to find it from the existing state. Since neither of these will be found the provider will fallback to default value of 0.Example:
This PR fixes the issue by letting the Google Container API to decide what the value is for existing clusters, which is 110 in this case. If the value is not defined in the Terraform configuration then it won't be used either.